home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HPAVC
/
HPAVC CD-ROM.iso
/
RA2HINTS.ZIP
/
RA2_ZLAB.ARJ
/
RA-ZLAB.DOC
< prev
next >
Wrap
Text File
|
1993-02-28
|
6KB
|
141 lines
┌────────────────────────────────────────────────────────────────────────┐
│ │
│ Docs for using ZipLab 2.0ß as an upload scanner with RemoteAccess 2.00 │
│ │
│ written by Mark Kerr │
│ @ 2:440/59 73:7440/1 │
│ │
└────────────────────────────────────────────────────────────────────────┘
INCLUDED FILES:-
Ra-zlab.doc - you're reading it
Pad.1 - Pad file for Com1
Pad.2 - Pad file for Com2
Pad.3 - Pad file for Com3
Zlab000.cfg - my Ziplab configuration
test.bat - The batch file I call from RemoteAccess to test files.
A new feature in RemoteAccess is the ability to have Uploaded files scanned
or manipulated, whilst the user is online or after logoff. ZipLab has the
ability to check archives for viruses and much more. If the file fails on
any check RemoteAccess will move it to a specified area. ZipLab also will
tell the User in a nice fashion what is happening, much nicer than sitting
staring at a prompt.
The following has been written with a multi-node system in mind, but should
work on a single line system.
Starting with version 1.9C of ZipLab Plus, it expects to find a 198 line
long version of PCBOARD.DAT, rather then the standard 152 line long version
which most door converters create. Starting with PCBoard 14.5, there is
extra information at the end of the PCBOARD.DAT, which among other things
defines the com port address and IRQ. ZipLab reads this now in order to be
compatible with non-standard com ports. Line 158 is the IRQ and line 159
is the port address.
After creating a 152 line PCBOARD.DAT file with a door converter, you must
tack on lines 153-198 to the end of it by using the DOS copy command.
Since the addon file will be differnt for each line, depending on the
com port address and irq, you will need 1 addon file for each com port in use.
There are 3 sample pad files included here, which should be copyed to
your ZIPLAB directory.
PAD.1 is currently set for COM1, 3F8, IRQ4
PAD.2 is currently set for COM2, 2F8, IRQ3
PAD.3 is currently set for COM3, 3E8, IRQ5
You may edit these and make additional copys for more nodes of course.
Once you have got full versions of pcboard.dat residing in your node
directories you can change the dm commandline in test.bat from PCB14 to
PCB14C this will stop dm creating the .dat file and you therefore can
rem out the appropriate portion of the test.bat. This will only work if you
are using a locked baud rate as the pcboard.dat contains the baud rate.
You could obviously? have all the PCBoard files reside in the ziplab
directory, but you can figure that one out if you wish to do so :-).
In earlier versions of this archive I incorrectly stated that Ziplab required
an environment variable set. This was incorrect and has been removed from the
sample batch file.
Obviously you will have to configure Ziplab for your own preferences and in
doing so you will realise you do not have to name its .cfg files ptest?
I have included a sample of one of my own Ziplab .cfg files.
Just alter the sample test.bat to reflect your filenames and directories.
REMOTEACCESS setup
------------------
RACONFIG -> OPTIONS -> FILES -> UPLOAD SCAN entry is
*C /c d:\zlab\test.bat *N @ *P *M
The *N is used by test.bat to find the pcboard files for that node.
The *P is used by test.bat to use the correct pad.? for that nodes com port.
The @ is used to pass ZipLab the filename for testing.
RACONFIG -> MANAGER -> LANGUAGES -> LANGUAGE -> LANGUAGE TEXT
change line 637 to something like:
Failed upload scan because: ^K!FAIL|
This uses a file created by the test.bat to display to the user the reason
for failure (not always virus infection).
I have RemoteAccess set to flag the file as unavailable and move it to a
badfiles area.
See included test.bat for details.
---------------------------------
My directory structure is as follows:-
d:\ra -system directory
d:\ra\txtfiles -text files directory
d:\ra\node1 -node dir
d:\ra\node2 -node dir
d:\ra\node3 -node dir
d:\zlab -ziplab directory (contains pad.* zlab*.cfg zlab.exe)
and test.bat
d:\upload -Ra's upload directory
d:\upload\temp -Where ZipLab moves bad files
d:\zlab\zlab.log -A log file I create to store reason for failure.
d:\zlab\giftest.log -The logfile giftest creates
Thanks, Credits, Software etc etc
---------------------------------
Thanks to Mike Ehlert for the some of the doc's (stolen from zlab-ra) and
Mark Anderson for the original :-) batch file, pad.1, and help.
RemoteAccess 2.? Andrew Milner :-)
The following programs are used in test.bat. Errlvl.zip and eyermv24.zip
could be replaced by other programs to set errorlevels and move files.
Programs used available for download or Freq @2:440/50 73:7440/1
errlvl.zip 3k by Zachary E. Stemich - sets dos errorlevel
DM532.arj 104k by Michael P. Otto - converts bbs info
ZL2B0117.zip 389k by Jeffrey S. Morley - checks archives
Eyermv24.zip 9k by Bob Eyer - moves files